Skip to content

fix(ci): wire extension publishing to release via workflow_call#38

Merged
ryanbas21 merged 1 commit into
mainfrom
fix/extension-publish-trigger
May 12, 2026
Merged

fix(ci): wire extension publishing to release via workflow_call#38
ryanbas21 merged 1 commit into
mainfrom
fix/extension-publish-trigger

Conversation

@ryanbas21
Copy link
Copy Markdown
Owner

Summary

  • publish-extension.yml never triggered because GITHUB_TOKEN-created releases don't fire release: [published] events for other workflows (GitHub docs)
  • Replaces release: [published] with workflow_dispatch (manual trigger) + workflow_call (chained from release)
  • Adds publish-extensions job to release.yml that fires after changesets publishes, using secrets: inherit

After merging, run gh workflow run publish-extension.yml to publish extensions for the current 1.0.0 releases.

Test plan

  • Merge PR
  • Manually trigger: gh workflow run publish-extension.yml
  • Verify Chrome, Firefox, and VS Code extension publish jobs succeed
  • On next changeset release, verify publish-extensions job runs automatically

🤖 Generated with Claude Code

GITHUB_TOKEN-created releases don't trigger other workflows, so the
publish-extension workflow never ran after changesets published packages.

- Replace release[published] trigger with workflow_dispatch + workflow_call
- Chain publish-extensions from release.yml when changesets publishes
- Pass secrets with secrets: inherit for store credentials

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@ryanbas21 ryanbas21 merged commit 7d47f17 into main May 12, 2026
1 check passed
@ryanbas21 ryanbas21 deleted the fix/extension-publish-trigger branch May 12, 2026 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant